fix: Opening statement character limit 40960#3790
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| prologue = serializers.CharField(required=False, allow_null=True, allow_blank=True, max_length=40960, | ||
| label=_("Opening remarks")) | ||
| knowledge_id_list = serializers.ListSerializer(required=False, child=serializers.UUIDField(required=True), | ||
| allow_null=True, |
There was a problem hiding this comment.
The change from max_length=102400 to max_length=40960 in the prologue field seems reasonable if you want to expand the character limit. However, ensure that this new limit will be sufficient for your needs and does not lead to unnecessary data storage. There are no other immediate issues with the provided code.
1 participant
fix: Opening statement character limit 40960